Attach prebuilt libraries to GitHub releases #300
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This adds a step to the release process that will attach the static
libsqlite3.abuilds to that release. After the first release using this, I'll add build logic to download from that release instead rebuilding from scratch on developer machines.Downloading these files instead of compiling them locally should speed up our local workflow. Especially since the SQLite3MultipleCiphers build for the JVM will also require additional toolchains and only work on macOS hosts, downloading would also make it easier to contribute to the SDK.
This also changes a few references from the
:coreproject to:common. Since the Supabase, Room and SQLDelight projects only need the:commonproject, this will allow them to be used with the encryption variant of the SDK.